Skip to content

feat: NEXT_PUBLIC_REQUIRE_EMAIL_VERIFICATION/EMAIL_FROM#156

Merged
dory-finn merged 1 commit intodorylab:mainfrom
chollinger93:chollinger93/disable-email-verification
Apr 7, 2026
Merged

feat: NEXT_PUBLIC_REQUIRE_EMAIL_VERIFICATION/EMAIL_FROM#156
dory-finn merged 1 commit intodorylab:mainfrom
chollinger93:chollinger93/disable-email-verification

Conversation

@chollinger93
Copy link
Copy Markdown
Contributor

@chollinger93 chollinger93 commented Apr 4, 2026

What

I tried self hosting this (seems like a cool project, thank you) but couldn't get past the demo screen, since email validation is required, but the sender email is also hard-coded.

image

This lets you configure both as:

EMAIL_FROM=example@example.org
NEXT_PUBLIC_REQUIRE_EMAIL_VERIFICATION=false

How

Followed the pattern of adding the environment variables as constant where they're used. I'd suggest centralizing the data model.

Test

docker run  \
  -p 3001:3000 \
  -e DS_SECRET_KEY="$(openssl rand -base64 32 | tr -d '\n')" \
  -e BETTER_AUTH_SECRET="$(openssl rand -hex 32)" \
  -e BETTER_AUTH_URL="http://localhost:3000" \
  -e DORY_AI_PROVIDER=openai \
  -e DORY_AI_MODEL=gpt-4o-mini \
  -e DORY_AI_API_KEY=your_api_key_here \
  -e DORY_AI_URL=https://api.openai.com/v1 \
  -e NEXT_PUBLIC_REQUIRE_EMAIL_VERIFICATION=false \
  $(docker build -q .)
image image image

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 4, 2026

@chollinger93 is attempting to deploy a commit to the DoryFinn's projects Team on Vercel.

A member of the Team first needs to authorize it.

@dory-finn
Copy link
Copy Markdown
Contributor

Thanks a lot for trying to self-host Dory — really appreciate it!

You're absolutely right. The current demo setup requires email verification, and the sender email is unfortunately hard-coded, which makes self-hosting difficult in this flow. That’s definitely not ideal.

Thanks again for pointing this out — super helpful feedback 🙏

@dory-finn dory-finn merged commit 88cad9d into dorylab:main Apr 7, 2026
0 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants